+++ /dev/null
-<para>
-When this option is specified, each non deleted waypoint is moved over the
-closest segment, or over the nearest point if <option>points</option> option
-is used.
-</para>
-<para>
-With the <option>rte</option> and <option>trk</option> options, if
-is possible, altitude, creation_time and microsecond fields of waypoints
-are updated by interpolation.
-</para>
-<para>
-This is most useful if you are trying to obtain the closest points in
-a road to some places. Or if you want to know the step times on some
-places over the tracks. Also to transform waypoints in Garmin course points
-(see <link linkend="fmt_gtrnctr">gtrnctr</link> and
-<link linkend="fmt_garmin">garmin</link> format).
-</para>
+++ /dev/null
-<para>
-When this option is specified the routes contains the vertices of the arc.
-If there are several routes then it is assumed that there is a gap between
-each of them.
-</para>
+++ /dev/null
-<para>
-When this option is specified the tracks contains the vertices of the arc.
-If there are several tracks then it is assumed that there is a gap between
-each of them.
-</para>
+++ /dev/null
-<para>
-This format supports reading and writing wayponts to
-<ulink url="http://www.bushnell.com/products/gps/">Bushnell GPS</ulink>
-receivers, notably the <productname>Onix 400</productname>.
-</para>
-<para>
-It's an oddity for many GPSBabel norms that this format requires each
-waypoint be in a separate file. Our "output filename" argument, -F is
-modified to take an "output filename template". The output filename
-you specify will have a dash, and a sequentially increasing integer,
-and the ".wpt" extension appended to it. When the names are shown on
-the GPS itself, the shortnames from the source format are used and not these
-"made up" names.
-</para>
-<example id="bushnell-output">
-<title>Command showing writing to Bushnell files</title>
-<para>
-Consider the case where 'whatever.gpx' holds three waypoints.
-<userinput>
- gpsbabel -i gpx -f whatever.gpx -o bushnell -F /Volumes/Bushnell/WAYPOINT/whatever
-</userinput>
-will result in "whatever-0.wpt", "whatever-1.wpt", and "whatever-2.wpt" being
-created in that directory.
-Windows users may prefer the spelling:
-<userinput>
- gpsbabel -i gpx -f whatever.gpx -o bushnell -F e:/WAYPOINT/whatever
-</userinput>
-</para>
-
-<para>
-At least for the 200CR, the directory name used by the device is "WAYPOINT"
-in the root directory. It's also worth mentioning that its USB Mass Storage
-protocol appears to not work on (at least) Snow Leopard 10.6.2. It's not
-known if other Onix models have a more compatible USB implementation.
-</para>
-
-
-</example>
+++ /dev/null
-<para>
-This format supports tracks from
-<ulink url="http://www.bushnell.com/products/gps/">Bushnell GPS</ulink>
-receivers, notably the <productname>Onix 400</productname>.
-</para>
-<para>
-This format reads individual .trl files as written by the GPS. As this is
-a reverse-engineered format, it's not understood how (or even if) long
-tracks, in
-particular, span multiple files so initially this format is most effective
-on tracks under a few thousand points.
-</para>
-<para>
- When writing tracks, a maximum of 4502 points is supported as this is the
- most we believe these units can represent in a track.
-</para>
-<para>
- The output base filename, converted to uppercase and stripped of
- everything but letters and digits, is used for the trail name inside
- the file itself.
-</para>
+++ /dev/null
-
-
-
- <para>This is the format used by <productname>CoastalExplorer</productname>. The
-format is XML with items uniquely identified by Windows-style UUIDs.
-<ulink url="http://www.rosepointnav.com">http://www.rosepointnav.com</ulink>
- </para>
-
+++ /dev/null
-<para>
- This format supports flight analysis data from the
- <ulink url="http://www.seeyou.ws/">See You</ulink>
- program.
-</para>
-<para>
- Position information is preserved, but the aviation-specific
- information such as runway length and airport frequency, are
- written as blanks and ignored on read.
-</para>
-<para>
- Tasks are not supported.
-</para>
-
+++ /dev/null
-<para>
- The <ulink url="http://www.mglavionics.co.za/">MGL Avionics</ulink> format holds waypoints or routes. These routes can be loaded by the MGL Stratomaster Enigma EFIS series (
-<productname>Enigma</productname>,
-<productname>Odyssey</productname>,
-<productname>Voyager</productname>,
-<productname>Explorer</productname>).
-</para>
-<para>
- The format is designed for microcontrollers. The use is free for any non-military application. You can find a detailed description in the <ulink url="http://www.mglavionics.co.za/Docs/Enigma%20Waypoint%20format.pdf">MGL Documentation</ulink>.
-</para>
+++ /dev/null
-<para>
-This format supports Garmin FIT activity files, defined as part
-of the ANT standard. These are generated by newer Garmin
-devices like the ForeRunner 110.
-</para>
+++ /dev/null
-<para>
- This is the 'gpl' format as used in DeLorme mapping
- products. It is a track format and contains little more than the
- tracklog of a GPS that was attached while driving.
- <ulink url="http://www.frontiernet.net/~werner/gps/">frontiernet.net</ulink>
-</para>
-
+++ /dev/null
-
-
-
- <para>HSA Systems Endeavour Navigator format - will import both
-the old version 4.x binary files, and the newer XML based ones. Only
-writes the new XML (5.0 and above) format. (use the .exp
-extension)</para>
-
+++ /dev/null
-<para>Reads the binary format of the <productname><ulink url="http://www.xaiox.com/itracku_sirf3.htm">XAiOX iTrackU BLUETOOTH GPS-RECEIVER SiRF III</ulink></productname> data logger.</para>
-<example id="itracku-bin">
- <title>Command showing reading an itracku data file.</title>
- <para><userinput>gpsbabel -i itracku-bin -f itracku.bin -o gpx -F out.gpx</userinput></para>
-</example>
+++ /dev/null
-
- <para>Support for Kartex 5 trackfiles. For more info see <link linkend="fmt_kwf2">kwf2</link>.</para>
-
+++ /dev/null
-
-
-
- <para>Support for Kartex 5 waypoint files. Kartex is a Swedish
- map and GPS positioning system. GPSBabel can read and write
- files from Kartex 4 and 5 with WGS84 coordinates. UTM or
- Swedish grid are not supported.
- </para>
-
+++ /dev/null
-<para>
- <ulink url="http://www.mapking.com/en/">Mapking</ulink> provides a set of tools for GPS
- navigation. Â The location of distributed maps is mainly in Asia, so the software seems
- not (yet) well known in Europe or US. Â Some of the GPS tools (e.g. Mapking 2007 for Windows Mobile)
- can also be used to write waypoints and save them under the .tr7 format which can be translated by GPSBabel.
-</para>
+++ /dev/null
-<para>
- This is the waypoint file format for Navigon units such as the Navigon 7100.
-</para>
-<para>
- To actually manipulate the file on the unit, use a USB cable or SD card
- reader and work with <filename>MN6\Settings\Favorites.storage</filename>
- The waypoints are be created with a minimal amount of data; the unit will
- fill in the other fields on use. The other fields appear to be data the
- unit infers, such as nearby streets.
-</para>
-<para>
- Note that this is the waypoint/placemark format (.storage) and not the
- route file format (.rte, .mn4) that is used by routes.
-</para>
+++ /dev/null
-<para>
- <ulink url="http://www.navitel.su">Navitel</ulink>Navigator is very popular navigation
- software in Russia and it's neighbors.
-</para>
-<para>
- This binary format only stores the latitude and the longitude of a trackpoint and is
- limited to 10000 points per file.
-</para>
+++ /dev/null
-<para>
-This format reads summary files from <productname>NetStumbler</productname>
-<productnumber>0.4</productnumber> or <productname>MacStumbler</productname>.
-</para>
-<para>
-The default behavior when creating waypoints is to use the SSID for
-the short name, and information about the access point for the
-description. When the SSID is not unique, is not available, or
-consists of whitespace, a short name is synthesized.
-</para>
-<para>
-Different icons are assigned to encrypted,
-non-encrypted, stealth, and non-stealth access points; these may be
-changed with options.
-</para>
-<para>
-<ulink url="http://www.netstumbler.com/">NetStumbler</ulink>
-</para>
-<para>
-<ulink url="http://www.macstumbler.com/">MacStumbler</ulink>
-</para>
+++ /dev/null
-
-
-
- <para>This is a CSV format from the National Imagery and Mapping
-Agency.</para>
-
+++ /dev/null
-<para>
-Because the format supports only one route, this option may be used
-on output to select a single route from a collection of
-routes read from a more expressive format. If you have, say, a
-<link linkend="fmt_gpx">gpx</link> file that contains two routes, you may
-use this option to write them one at a time to individual files.
-</para>
-<para><userinput>gpsbabel -i gpx -f routes.gpx -o bcr,index=1 -F route1.bcr -o bcr,index=2 -F route2.bcr</userinput></para>
-
+++ /dev/null
-<para>
-This route specifies the name of the route. This is particularly useful if
-the route came from an input format that did not support named routes, but
-it may also be used to rename a route.
-</para>
+++ /dev/null
-<para>
-This option causes GPSBabel to use the short name of the waypoint instead
-of the description.
-</para>
+++ /dev/null
-<para>
-This option instructs GPSBabel to use a different value for the radius of
-the earth when converting between the Mercator projection and geographic
-coordinates. The default value is 6371000.0 meters.
-</para>
-<para>
-Careful experimentation with this value may help to reduce conversion
-errors.
-</para>
+++ /dev/null
-<para>
-This option will add the icon description to the end of the waypoint
-description on output. This can be useful if the icon is used to convey
-important information about the waypoint. For example, the icon might be
-"found geocache" or "unfound geocache"; it might be useful to know that when
-looking at a list of icons in Cetus.
-</para>
+++ /dev/null
-<para>
-This option specifies the database name for the output file. This name is
-not the same thing as the file name on your computer; this is the name that
-appears in the file browser on your handheld.
-</para>
-
+++ /dev/null
-<para>
-This option specifies a name for the "Not Assigned" category in the Palm
-database. The default is "Not Assigned".
-</para>
+++ /dev/null
-<para>
-This 1/0 option, defaulting to if not provided, tells GPSBabel to
-use its own logic when sending data it can deduce is a geocache to
-the device. If false, any icon data present in the source data will
- be used instead. If you've taken control of the icon data, you are
- responsible for providing valid icons; GPSBabel will make no attempt
-to purify what gets sent.
-</para>
+++ /dev/null
-<para>This option returns the current position as a single waypoint.</para>
+++ /dev/null
-<para>
- When set to true, this places the "HINT:" entry from a geocaching.com
- pocket query at the end of the screen (scroll up for quick access) like
- Cache Register and Topo7 do instead of at the top as Topo8 does.
-</para>
+++ /dev/null
-<para>
- When set to true, this places the "HINT:" entry from a geocaching.com
- pocket query at the end of the screen (scroll up for quick access) like
- Cache Register and Topo7 do instead of at the top as Topo8 does.
-</para>
+++ /dev/null
-<para>
- When set to true, this includes Groundspeak logs from GPX pocket queries
- when writing to DeLorme devices that support the extended features introduced
- in firmware version 2.5 for the PN-40 and PN-30 and in 1.6 for the PN-20.
-</para>
+++ /dev/null
-<para>
- Use long waypoint notes, overriding the built-in version check (which is
- reverse engineered) that tests if the unit can handle the waypoint comments
- longer than 800 bytes.
-</para>
-<para>
- This option will probably go away in time as most units get upgraded to
- the capabilities of the 2.5 version of the PN-40 and PN-30 or version 1.6
- for the PN-20.
-</para>
+++ /dev/null
-<para>
- When present on the command line and sending routes with -r, this will erase
- all routes in the receiver before sending the new ones.
-</para>
-
+++ /dev/null
-<para>
- When present on the command line and sending tracks with -t, this will erase
- all tracks in the receiver before sending the new ones.
-</para>
+++ /dev/null
-<para>
- When present on the command line and sending waypoints (either explicitly
- via -w or as the default), this will erase
- all waypoints in the receiver before sending the new ones.
-</para>
+++ /dev/null
-<para>
- Convert track number 'index' from source into dmtlog format.
-</para>
-<para>
- The known variants of Tracklog 'digital mapping' files supports only
- one track per file. If you have more than one track in source
- (f.e MapSource and many others can do such heavy things), you
- can specify which track should by used for the conversion.
-</para>
-<para>
- The default index is 1 (the first track of a possible list of tracks).
-</para>
+++ /dev/null
-<para>
-This option specifies the name of the category in which to place the
-waypoints. If this option is not specified, the default category is
-"Cache".
-</para>
-
+++ /dev/null
-<para>
-This option specifies the database name for the output file. This name is
-not the same thing as the file name on your computer; this is the name that
-appears in the file browser on your handheld.
-</para>
-
+++ /dev/null
-<para>
-This option specifies the database name for the output file. This name is
-not the same thing as the file name on your computer; this is the name that
-appears in the file browser on your handheld.
-</para>
-
+++ /dev/null
-<para>
-This option specifies the database name for the output file. This name is
-not the same thing as the file name on your computer; this is the name that
-appears in the file browser on your handheld.
-</para>
-
+++ /dev/null
-<para>
-Adds a constant value to every altitude. You can specify negative numbers to subtract the value.
-</para>
-<para>
-If no unit is specified, meters (m) are assumed. You can override this by attaching a "f" for feet to the number.
-</para>
+++ /dev/null
-<para>
- Subtracts the WGS84 geoid height from every altitude.
-</para>
-<para>
- For GPS receivers like the iBlue747, this corrects the logged altitudes to height above mean sea level.
-</para>
+++ /dev/null
-<para>
-Because the format supports only one track, this option may be used
-on output to select a single track from a collection of
-tracks read from a more expressive format. If you have, say, a
-<link linkend="fmt_gpx">gpx</link> file that contains two tracks, you may
-use this option to write them one at a time to individual files.
-</para>
-<para><userinput>gpsbabel -i gpx -f tracks.gpx -o ignrando,index=1 -F track1.txt -o ignrando,index=2 -F track2.txt</userinput></para>
-
+++ /dev/null
-<para>
-Use this option to the description of the track which is text appears just below the track title in the track list on the device.
-</para>
-
-
+++ /dev/null
-<para>
- Use this option to set the title of the track.
-</para>
+++ /dev/null
-<para>
- This option isn't entirely clear. It appears to be a unique number
- for each track that is used for coloring on the main display. So if you
- want two tracks to have different colors, set the track numbers to
- different values.
-</para>
-<para>
- If you can provide a better description of this option, please do contact
- us.
-</para>
+++ /dev/null
-<para>Specifies a backup file for the binary logger data. New waypoints from the logger will be appended to an existing
-backup file. This allows you to create "endless" binary logger files which, for example, could contain the waypoint data of a whole year.</para>
-<para>The backup file can be read with gpsbabel by using the itracku format.</para>
-
-<example id="itracku-backup">
- <title>Download from the data logger while and append the new binary logger data to a backup file. Read the contents of the backup file.</title>
- <para><userinput>gpsbabel -i itracku,auto,backup=itracku.bak -f dummy -o gpx -F out.gpx</userinput></para>
- <para><userinput>gpsbabel -i itracku -f itracku.bak -o gpx -F out.gpx</userinput></para>
-</example>
-
+++ /dev/null
-<para>
- Providing a filename to this option will append the input to a backup file.
-</para>
+++ /dev/null
-<para>
- When used in conjunction with the "backup" option to this format, it
- will process only waypoints that don't already exist in the backup file.
-</para>
+++ /dev/null
-<para>Will only pass waypoints along to filters and output formats that are not new, i.e. that are not already stored in the
-backup file. This option can only be used with the backup option.</para>
-<para>Using this option allows you to output the waypoints of your latest trip with gpsbabel while keeping an endless log of all waypoints
-in the backup file.</para>
-
-<example id="itracku-new">
- <title>Download from the data logger and append the new logger data to a backup file. Output only the new
- waypoints.</title>
- <para><userinput>gpsbabel -i itracku,auto,backup=itracku.bak,new -f dummy -o gpx -F out.gpx</userinput></para>
-</example>
-
-
+++ /dev/null
-<para>
-This option specifies if you want to write the compressed binary format (WBXML)
-instead of the XML format. However, most current Nokia phones do only support
-the XML format (confirmed with N82 and N95).
-</para>
-<para>
-This option has no effect when used for input, only reading the traditional XML
-format is supported.
-</para>
+++ /dev/null
-<para>
- By default GPSBabel creates only 'un-locked' items.
-</para>
-<para>
- Sample command to write an mmo file with 'locked' items:
-</para>
-<para>
- <userinput>
- gpsbabel -i gpx -f in.gpx -o mmo,locked=y -F out.mmo
- </userinput>
-</para>
+++ /dev/null
-<para>
-Two major strains of Mobile Mapper files have been identified in the wild. Version 17 is reported as "Memory Map OS Edition 2004, Versio 4.2.3 Build 432" and version 18 is used by the large majority of current files. We can read either and when writing, we write version 18 by default.
-</para>
-<para>
-If you have a particularly old Mobile Mapper installation, it may complain "This file was created with a newer version of the Software" when reading our output.You can get around this if force GPSBabel to create the old format with this option.
-</para>
-<example id="mmo_ver">
-<title>Forcing creation of old Mobile Mapper files</title>
-<para>
- gpsbabel -i gpx -f whatever.gpx -o mmo,ver=17 -F whatever.mmo
-</para>
-</example>
+++ /dev/null
-<para>
- This option can be useful, if you want to convert a big file with a lot of entries.
- By default GPSBabel creates only 'visible' items.
-</para>
-<para>
- Sample command to write an mmo file with 'invisible' items:
-</para>
-<para>
- <userinput>
- gpsbabel -i gpx -f in.gpx -o mmo,visible=n -F out.mmo
- </userinput>
-</para>
-
+++ /dev/null
-<para>The default is to autodetect the baudrate, but that can take a few seconds. If you know the baudrate of the device it is faster to specify it explicitly.</para>
-<para>Only valid when using a USB device as input.</para>
+++ /dev/null
-<para>This option processes a set of Locus fixes, by downloading it from an
-attached USB device or by reading records stored in a normal file.</para>
-<para>You might want to disable this option if all you want to do is erase the memory
-or display the device status. Downloading a large dataset can take several minutes
-and while that is happening no other device commands can be executed.</para>
+++ /dev/null
-<para>This option sets logging on the device to on or off. Setting the logging off does not erase the saved fixes.</para>
-<para>Only valid when using a USB device as input.</para>
+++ /dev/null
-<para>This option erases the track log from the device after download.</para>
-<para>Only valid when using a USB device as input.</para>
+++ /dev/null
-<para>This option displays the status of the device after the download is complete. Status includes firmware version, number of log records in memory, interval between fixes, etc.</para>
-<para>Only valid when using a USB device as input.</para>
+++ /dev/null
-<para>
- If this option is present, retired (archived) caches will be suppressed on write.
-</para>
+++ /dev/null
-<para>
-This option specifies the name of the icon to use for
-non-stealth, encrypted access points.
-</para>
+++ /dev/null
-<para>
-This option specifies the name of the icon to use for
-non-stealth, non-encrypted access points.
-</para>
+++ /dev/null
-<para>
-This option specifies the name of the icon to use for
-stealth, encrypted access points.
-</para>
+++ /dev/null
-<para>
-This option specifies the name of the icon to use for
-stealth, non-encrypted access points.
-</para>
+++ /dev/null
-<para>
-This option causes GPSBabel to use the MAC address as the short name for the
-waypoint. The unmodified SSID is included in the waypoint description.
-</para>
+++ /dev/null
-<para>
-If you would like the generated bookmarks to start with
-the short name for the waypoint, specify this option.
-</para>
-<para>
-This is particularly useful when used in combination with the 'sort'
-filter.
-</para>
-
+++ /dev/null
-<para>
-This option specifies the internal name for the document. This is the name
-that appears in your document reader, not the name of the file that is created
-on your computer.
-</para>
+++ /dev/null
-<para>
-Use this option to encrypt hints from Groundspeak GPX files.
-</para>
+++ /dev/null
-<para>
-Use this option to include Groundspeak cache logs in the created document.
-</para>
+++ /dev/null
-<para>
-To suppress the dashed lines between waypoints, use this option.
-</para>
+++ /dev/null
-<para>
-This option specifies the input and output format for the date. The format
-is written similarly to those in Windows. An example format is "YYMMDD".
-</para>
+++ /dev/null
-<para>
- This option specifies the database vehicle/transportation icon name for the
- output file. This name is not for individual points, but for the entire
- database; this is the icon that appears in the points
- databases/tracks/routes screens besides the database name, in the Pathaway
- application on your handheld.
-</para>
+++ /dev/null
-<para>
-This option specifies the database name for the output file. This name is
-not the same thing as the file name on your computer; this is the name that
-appears in the file browser on your handheld.
-</para>
-
+++ /dev/null
-<para>
- The deficon option is used to control the icon output when writing to this format. It overrides any icon information that might be present in the source data.
-</para>
+++ /dev/null
-<para>
- This option allows you to specify the length of waypoint names written to this format when used with the <option>-s</option> option.
-</para>
+++ /dev/null
-<para>
-This option specifies the database name for the output file. This name is
-not the same thing as the file name on your computer; this is the name that
-appears in the file browser on your handheld.
-</para>
-
+++ /dev/null
-<para>
- With this option you can specify the name of the folder
- where the waypoints are placed.
-</para>
-<para>
- This name is also limited to 16 characters.
-</para>
+++ /dev/null
-<para>This option lets you read the control points
-(start, end, vias, and stops) for your route as well as the route
-itself. The default for this option is 'none', which won't read the
-control points. You may also specify 'waypoints', which reads the
-control points as waypoints, or 'route', which creates an extra route
-named 'control points' containing just the control points in order.
-Note that if your goal is to create an arc or other CSV file, you
-should use 'none' (or not use this option, which is the same
-thing.)</para>
-
+++ /dev/null
- <para>This option causes GPSBabel to create separate
-routes for each street, creating a new route at each turn point. For
-obvious reasons, 'split' cannot be used at the same time as the
-'turns_only' or 'turns_important' options.</para>
-
+++ /dev/null
- <para>This option causes GPSBabel to read the route as if
-it were a track, synthesizing times starting from the current time, using
-the estimated travel times specified in your route file (you can change your
-travel speeds in the DeLorme product you used to create the route file.)</para>
-
+++ /dev/null
- <para> This option only makes sense in
-conjunction with the 'simplify' filter. It ensures that the route
-simplification process will remove the points corresponding to turns
-only after it has removed all other route points.
-</para>
-
+++ /dev/null
- <para> This option causes GPSBabel to read only the
-waypoints associated with named turns. This should create a list of
-waypoints that correspond to the itinerary from Street Atlas.</para>
-
+++ /dev/null
-<para>
-This option may be used to eliminate calculated route points from the route.
-</para>
+++ /dev/null
-<para>
-This option lets you configure how many digits GPSBabel uses for numbering generated route point names.
-</para>
-<para>
-When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices.
-</para>
-<para>
-Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option.
-</para>
-<example id="transform_rptdigits">
-<title>Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers.</title>
-<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx</userinput></para>
-</example>
+++ /dev/null
-<para>
-With this option you can decide to let GPSBabel name generated route points according to their source track name.
-</para>
-<para>
-GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>
-<para>
-Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes.
-</para>
-<example id="transform_rptname">
-<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>
-<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx</userinput></para>
-</example>
+++ /dev/null
-<para>
-This option specifies the data format version for the input and the output file.
-Valid values are 1 (without altitude) or 2 (with altitude). 1 is the default.
-</para>
+++ /dev/null
-<para>
- This option lets you specify the database name written into the file.
-</para>
-
+++ /dev/null
-<para>This is the format for the Ricoh 500SE GPS logging camera.
-</para>
-<para>
- This camera creates log files on the SD card in a folder name "GPSLOG" that
- are named "YYMMDDNN.LOG" where NN increments from 00 through 99. The camera
- appends new tracks into the current file, hence the "new track" field. When
- the current file reaches about 500K, NN increments and logging continues into
- the next file. Therefore, there may be multiple tracks in each log
- file, and tracks may span one or more files.
-</para>
-<para>
- GPSBabel will recognize the "new track" field and will generate a new track,
- so if you specify multiple files in the correct order, your tracks will be
- automatically split sensibly.
-</para>
-<para>
-For additional tips, see the
- <ulink url="http://wiki.openstreetmap.org/wiki/Ricoh_500SE_GPS_Log">OpenStreetMap page on Ricoh 500SE</ulink>.
-</para>
-
+++ /dev/null
-<para>
- With this format we support Sportsim trackfiles located in zipped .ssz archives.
-</para>
-<para>
- Currently we cannot read zipped files directly with GPSBabel. So you have
- to extract the archive before you can use any file. The trackfiles have .txt extensions.
-</para>
-<para>
-<ulink url="http://www.sportsim.com/web/index.php?url=about">From the Sportsim homepage:</ulink>
-</para>
-<para>
- Sportsim provide software applications and web-based graphically
- simulated performance information and image solutions to outdoor active people.
-</para>
+++ /dev/null
-<para>
- With this format you can read and write <ulink url="http://www.tomtom.com">TomTom</ulink>
- Points of Interest - POI (ascii) files.
- It is a simple text (csv) format with only latitude, longitude and a short name.
-</para>
+++ /dev/null
-<para>
- tomtom_itn can be used to read and write <ulink url="http://www.tomtom.com">TomTom</ulink> Navigator Itineraries (Routes).
-</para>
+++ /dev/null
-
-
-
- <para>This module reads .TPO files created by various editions
-of NG Topo!. For version 2.x files it will only read tracks. For
-version 3.x files it will read Tracks/Routes/Waypoints/Map
-Notes/Symbols/Text Notes. The latter three are converted to
-waypoints.</para>
- <para>2.x support contributed by Steve Chamberlin. 3.x support
-contributed by Curt Mills.</para>
-
-